>>78053994Go back to like the last three threads and open your fucking eyes you retarded faggot
>>78054910I've been digging around some of the files today, a LOT of the assembly is Real Mode dogshit recycled from pre-NT Windows, so I don't think we're gonna get a proper amd64 build working without porting a lot of that assembly to not use Real Mode registers after handoff to NTLDR. I'm not even sure if modern UEFI firmwares support direct execution of Real Mode code anymore unless the CSM is enabled, which I consider a security risk. I think it's best if we first get a fully working, clean i386 environment first. Then we can start looking at if it's even possible to get a fully working amd64 build with the code we have. There seems to be a lot of stuff missing, definitely not enough to even get a working amd64 or even Itanium build.
>>78056259It will be a mammoth task lasering off the M$ tattoos, but that's tomorrow's problem.
>>78057122This should probably the next priority after we get Sizzle (I can't fucking believe we're actually going with Sizzle) building cleanly. Any environment we actually manage to build is virtually worthless if it stops working after 30 days, and it's retarded to keep having to 'bypass' WPA/oobe when we can just find a way to patch it out. Sadly, a lot of M$ software relies on Windows Genuine Advantage, and will look for it during install. I know .NET 3.5 newer will look for WPA and fuck up your system if it doesn't find it.
>hardcode a VL keyWe shouldn't consider this a permanent fix. While it does work, it's messy and a workaround. We should definitely look to completely patch out WPA as best we can, not only for completeness but also because it results in smaller, more secure code and we won't have the stupid WPA services running in the background eating RAM and CPU cycles.
Fucking hell cunts I disappear for like 15 hours and we've already made a decent amount of progress. Autism is fucking based.
